home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr52
/
bblink16.zip
/
BBLINK.DOC
next >
Wrap
Text File
|
1993-04-16
|
21KB
|
818 lines
bBLINK v1.05
* Linker Utility by Bullet Software *
Clipper ver. s87 & 5.01
(all rights reserved)
BULLET SOFTWARE
10376 E. COLONIAL DR
SUITE 110
ORLANDO,FL 32817
(407) 277-5198
-----------------------[ Disclaimer ]-------------------------------
Bullet Software distributes this utility solely on an "as is"
basis and offers no warranties at all.
Bullet Software shall not bear any liability or responsibility to
any user or entity with respect to any liability, loss or
damage caused, or alleged to be caused directly, or indirectly
by this in this product, including but not limited to interruption
of services, loss of business or anticipatory profits or consequential
damages resulting from the use or operation of any of the functions
contained in this product.
Bullet Software makes no warranties, either expressed or implied
regarding this software product, it's merchantability and/or
it's fitness for a particular purpose. The user agrees that
Bullet Software shall not be held liable for any consequential
damages, even if Bullet Software has been advised of the possibility
of such damages.
By using this utility you acknowledge your agreement with all of
the above conditions.
-----------------------[ Authorization of Use] ----------------------
You may use bBLINK for a period of 30 days, after which time you
must either cease use or register your copy with Bullet Software.
Registration is accomplished by sending the current REGISTRATION
and ORDER form found at the end of this file. Also, for your
convenience you will find a file named ORDER.TXT in this
compressed file that you may type:COPY ORDER.TXT > PRN and it will
print out on your printer for you. Of course you may call to order
your registered version to receive it in a more timely fashion.
Orders will be filled only if accompanied by the current
registration fee.
bBLINK is NOT freeware. If you believe it has value to you, then
registration is in order.
Bulletin board services and other such services may charge a fee
no greater than disk and transfer charges for this product.
This is in NO WAY TO BE CONSIDERED AS payment for this product.
This product can ONLY be purchased from Bullet Software, any fee
you may have been charged by ANY ENTITY other than Bullet Software
for this product is not considered valid by Bullet Software or
the author of the this product.
-----------------------[ What is bBLINK ]-------------------------------
Zip file contents: bBLINK.EXE
bBLINK.DOC
ORDER.TXT
DISCLAIM.TXT
Copyright : Bullet Software
Orlando,FL
Purpose : Utility to create compile & link files quick and easy.
----------------------[ What is Required ]---------------------
Clipper.exe ver 5.01 or s87
Blinker.exe ver 1.50 or greater
make.exe any generic make utility
(clipper compatible)
This utility is to be used with BLINKER(tm) linker by
Assembler Manufacturers INC. this utility is designed
to aid users who are beginning to use BLINKER as well as
seasoned professionals.
Bullet Software is in NO WAY CONNECTED or INVOLVED WITH
the above mentioned company.
Bullet Software and Robert Morgan are the sole owner of the
source code and rights to this program.
---------------[ A Few Benefits of using BLINKER ]-------------------
NOTE:
These comments are from the Blinker documentation dated 1991
and are not to be considered as current.
BLINKER is a dynamic overlay linker which allows the
Clipper developer to easily and effectively overcome the 640KB
limit imposed by DOS on the personal computer.
Instead of having to structure an application into overlays
which are mutually exclusive and therefore may use the same
area in memory at run time, the developer simply specifies
which procedures or functions may be overlaid and leaves the
rest to the BLINKER overlay manager.
BLINKER performs the link phase of an application's compile and
link cycle, creating overlay units for the dynamic overlay
manager and linking the application two to four times as fast
as MS LINK (in itself at least three times as fast as PLINK86plus
and .RTLINK). At run time this results in a simpler, more compact
program which uses less memory much more efficiently than with
traditional linkers.
BLINKER may also be used to prepare a demonstration copy of an
application at link time without modifying the application code
in any way. The demonstration program may be restricted either
by the number of procedure or function calls, by the number of
minutes of execution time, or by an expiration date after which
the program will not run.
BLINKER provides profiling facilities allowing a user defined
Clipper procedure to be called each time any overlaid Clipper
procedure is called, without modification of the application
source code. This allows the developer to monitor an application
while it is running and record information such as how many
times each overlay was called and how many times it was loaded
from disk.
Assembler Manufacturers INC. may be contacted at:
3304 Nuttree Woods Drive
Midlothian, VA 23112
Tel. (804) 744-LINK
Fax (804) 744-3527
BBS (804) 744-2583
CIS 75140,1173
Foot note: 02/13/92
According to messages left on the BLINKER bbs there is to be a
release of Blinker version 2.0 very soon. It is also expected
that according to their usual professional standard of backward
compatibility Assembler Manufacturers INC. will allow you to
continue to use the same style of .lnk and .mak files for linking.
However, should this not be the case, we will immediately begin
work on producing a compatible version of bBLINK. We don't foresee
this to be valid, but, bBLINK will be compatible whatever the
case.
------------------------[ Using bBLINK ]-------------------------
1. Copy all of your program files (.prg's) into an EMPTY
work directory. (PRGS ONLY no other files!)
2. Copy bBLINK to a directory that DOS always has access to.
(Be sure bBLINK IS IN YOUR DOS PATH!)
3. Change to the work directory that contains your PRGS ONLY that you
want to create incremental linking files for and type bBLINK.
┌───────────────────────────────────────────────────────────────┐
│3a. ┌────────────────────────────────────────┐ │
│ │ * (FIRST TIME RUNNING bBLINK) * │ │
│ └────────────────────────────────────────┘ │
│ │
│ Enter the information for the questions as you are prompted. │
│ │
│ (This info will be saved.) │
└───────────────────────────────────────────────────────────────┘
The first run of bBLINK on your system will activate the setup
module. The questions are few, and direct to the point. I will
not go into the meaning of the terms used, such as path etc.,
if you don't understand these questions you should STOP NOW and
find someone who does. Have them help you do the install.
The only tip you should need is when entering a path DO NOT
include any file names these are ONLY PATHS.
bBLINK knows the name of the files it is looking for or you
will be given this option later.
NOTE:
The NON-REGISTERED version will have a registration screen
each time bBLINK is started. The registered version will not
have any introductory message whatsoever.
4. Enter your MAIN or (TOP) file name.
This information will be saved upon exit.
5. Select your libraries.
(press enter on highlighted library)
Select where to put the library in relation to the .LNK file.
a. SEARCH
b. ROOT
c. ALLOCATE
d. SECONDARY
Consult your BLINKER documentation for the meaning and use of
these terms. (we will not reinvent the wheel by trying to
explain these) Although a good tip is to have the NORTON
GUIDE that came with your BLINKER linker running in the back-
ground so you may refer to the meaning of these, and other
terms.
Once you have selected a library you will see the current
status position of the selected library in the .LNK file
in one of the boxes in the upper right. You will also notice
if you have a color monitor, they are of different colors.
This is based on their order of importance regarding memory
use and link priority.
If you have a NON REGISTERED version you will be restricted
to only one directory path for your library choices and only
three windows for library listings.
The registered version allows up to 4 directory paths for .LIB
files and has a separate window for the SEARCH allocation, (and
that's not the only differences).
6. Press the INSERT KEY to select THE BLINKER OPTIONS to add to your
.LNK file.
(press enter on the highlighted option)
If the option you have chosen requires more information from you,
another widow will pop up asking for your parameters for that
particular function (refer to your .ng for this).
If the option you have chosen is a simple command
'ie:BLINKER MESSAGE NOBLINK' then you will just see the window
BLINK at you (forgive the pun). Here again there is a distinct
difference between the REGISTERED and NON REGISTERED versions.
(continued)
In the NON REGISTERED VERSION there is no distinction made between
selected and un-selected options you just have to remember where
you are and what you have chosen. Also, there is no editor to
edit your chosen functions. (only an inconvenience) but having
the ability to edit is great to have.
7. Escape when done.
(file creation)
After you have entered all of your options for libraries and
blinker commands. You are ready to create 3 files which will
be used for compiling and linking.
1. BL?.BAT
2. BLINKMAK.
3. BLINK.LNK
If you have these files from a previous run of this program
and you wish to keep them for some reason you must rename
them to some other name because they will be over written
without any warning.
To quit and create your new .bat, .lnk and .mak files
simply hit escape. You will see a message indicating these
files have been created, the program then exits to DOS.
Before exiting you will notice a message indicating that you
should EXECUTE a specific file name, the file name will be
'BL?.BAT'. Where '?' is the first letter of your top file.
Let's say your top file name is TEST.prg, that means the name
of your batch file would be 'BLT.BAT' because the letter 'T'
is the first letter in your top file name.
The reason for the long explanation is so you can determine
in advance the name of your starting batch file in the event
you already have a batch file by that name that you wish to
keep. This is the only file that will have a different name
for each program you wish to compile.
8. Compiling and Linking
(executing the starting batch file)
To compile and link all of your modules just type the name
of your starting batch file and hit enter. If all is well
your program compiles and links as it should. If there are
errors in the programming code of course you will see the
errors and correct them.
----------------------[ A Word on Linking ]------------------
There are several ways to compile and link .prg files. The use
of .clp files, batch files and just a plain old command line
prompt. Which of these methods you use is entirely up to the
programmer although no attempt of supporting .clp files is
in this program they do have their place however.
We have found that the granular approach is much more effective
for our style of professional development and need for individual
control of each program module. It lends itself to extremely
easy maintenance of large programs, procedures and functions.
The greater level of granularity is worth the small price of
learning how to make it work for you. A program that has
30 - 40 individual functions is much easier to service and
debug if you are using the granular approach, also some word
processors complain if a text file is too large, or memory
starts getting too low to do anything.
Portability of your functions & procedures to other programs
and libraries is greatly enhanced because you can put your
cursor on it immediately rather than browsing through hundreds
of lines of source code and comments.
-------------------------[ Modifications ]---------------------
1. Changing the setup
Should you need to change your original parameters for paths
to your libraries, objs etc. you can re-enter the setup
module by typing the command line :bBLINK /s
2. File naming conventions
You may want to rename bBLINK to something less cumbersome,
like BLM.EXE or B1.EXE feel free to do so. But, DO NOT append
or change any of the files within the bBLINK15 compressed file.
3. Created files (.lnk .bat *.)
Browse the .LNK file, there are comments through out to guide
you through the logic. This will help you to grasp the command
format and style that will get a first time BLINKER user up and
running quickly.
(External files)
Each .lnk file you produce will have 2 lines included for your
ERRORSYS.OBJ and DEBUG.OBJ.
You will notice that the debug.obj and errorsys.obj have been
commented out. This is clearly so that you have the option of
including them in your final .EXE. If you want them in the
final product then just remove the '#' from in front of them.
These are used by Clipper Summer 87. Clipper 5.01 uses it's
own interactive CLD.exe but you can add your own special
debugging file in every program if you wish to use in conjunction
with CLD.exe.
Even if you only have 3 or 4 modules in your program bBLINK will
save you hours of typing over a years time.
--------------------[ Registered Features]----------------------
A few advantages of the registered version of bBLINK are as
follows:
1. Multiple data paths a the press of a key.
2. Script file editing and viewing on the fly.
3. Startup file creation options.
4. Unrestricted use of all functions and commands.
5. On-line tech support.
6. F1 key instant help.
7. Multiple configuration files (selectable).
8. Free upgrades on-line (current versions).
9. Discounts on other Bullet Software products.
10. Backward compatibility.
-----------------------[ 2 Programmers ]------------------------
pgmr1. Why should I use bBLINK?
pgmr2. Accomplish in seconds what it takes several minutes even
hours by hand, and with high tech accuracy.
pgmr1. I have done it for years myself why change?
pgmr2. You won't have all that redundant typing.
pgmr1. Gosh you are right, thanks
pgmr2. Your welcome
Note: the following prices are subject to change without notice
--------------------[ORDER REGISTRATION]-------------------
bBLINK Linker Utility Registration Order Form
Version 1.05
Please send the following:
[ ] Copies bBLINK Linker Utility @$39.00 ________ ea.
Shipping and Handling $ 3.50 ________
Total ________
Method of payment (circle one):
Money Ord. Check Visa MasterCard Amount Enclosed $_______
Phone Orders welcome. (407) 277-5198
Name_____________________________ Company ____________________
Address ___________________________ City ____________________
State _________ Zip ____________ Country __________________
Phone ( )____ _______
Card Number ________________________ Expiration Date _________
Signature __________________________________________________
Name on card ________________________________________________
Make Checks or Money Orders Payable to: Bullet Software
Where did you receive your copy of the software you are
registering?
_____________________________________________________________
Comments:
______________________________________________________________
______________________________________________________________
______________________________________________________________
Mail to:
Bullet Software
10376 E. Colonial Drive
Suite 110
Orlando,FL 32817